Rationale modeling for software process evolution
Identifieur interne : 003905 ( Main/Exploration ); précédent : 003904; suivant : 003906Rationale modeling for software process evolution
Auteurs : Alexis Ocampo [Allemagne] ; Jürgen Münch [Allemagne]Source :
- Software Process: Improvement and Practice [ 1077-4866 ] ; 2009-03.
English descriptors
- Teeft :
- Adaptive services grid, Aerospace engineering standards, Application engineering, Armbrust, Artifact, Best practices, Bruegge, Case studies, Common issues, Compliant, Computer science, Conceptual, Conceptual model, Conradi, Copyright, Database, Design rationale, Design rationale domain, Dutoit, Ecss, Ecss requirement, Ecss software engineering standards, Ecss standards, European workshop, Evolution, External services, Ground segments, Heuristic, Ieee, Ight software, International organization, John wiley sons, Lecture notes, Modeling, Ocampo, Organizational process, Pract, Process changes, Process description, Process element, Process elements, Process engineer, Process engineers, Process evolution, Process knowledge, Process model, Process model changes, Process model evolution, Process models, Rationale, Rationale information, Rationale management, Rationale modeling, Real project, Reference process, Reference process model, Research section, Research section rationale modeling, Same time, Second study, Semg, Softw, Software, Software developer, Software engineering, Software engineers, Software process, Software process evolution, Software process improvement, Software process technology, Software processes, Standardization, Study results, Such changes, Traceability, Traceability relationships, Understanding rationale information, Visualization.
Abstract
Evolving a software process without a retrospective on its evolution and, in consequence, without an appropriate understanding, can lead to important problems for a software development organization. Two examples of such problems are inefficient performance as a consequence of the arbitrary introduction of changes or difficulty in demonstrating compliance to a given standard. Capturing information on the rationale underlying process changes provides a means for better understanding process evolution. This article presents two studies aimed at understanding and identifying information needs for describing the rationale for process evolution. Additionally, it presents an approach for incrementally evolving processes supported by this rationale. This approach is derived from the results of the studies and a survey of related work. An application of the approach during the evolution of a reference process for developing service‐oriented applications is presented together with experience and open questions for future research work. Copyright © 2008 John Wiley & Sons, Ltd.
Url:
DOI: 10.1002/spip.387
Affiliations:
Links toward previous steps (curation, corpus...)
- to stream Istex, to step Corpus: 001F96
- to stream Istex, to step Curation: 001F70
- to stream Istex, to step Checkpoint: 000A12
- to stream Main, to step Merge: 003983
- to stream Main, to step Curation: 003905
Le document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">Rationale modeling for software process evolution</title><author><name sortKey="Ocampo, Alexis" sort="Ocampo, Alexis" uniqKey="Ocampo A" first="Alexis" last="Ocampo">Alexis Ocampo</name></author><author><name sortKey="Munch, Jurgen" sort="Munch, Jurgen" uniqKey="Munch J" first="Jürgen" last="Münch">Jürgen Münch</name></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:8A2034E007FE8B1CC78A54A20E455D4A2AA1D9A0</idno><date when="2009" year="2009">2009</date><idno type="doi">10.1002/spip.387</idno><idno type="url">https://api.istex.fr/ark:/67375/WNG-ZLT58DDF-D/fulltext.pdf</idno><idno type="wicri:Area/Istex/Corpus">001F96</idno><idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Corpus" wicri:corpus="ISTEX">001F96</idno><idno type="wicri:Area/Istex/Curation">001F70</idno><idno type="wicri:Area/Istex/Checkpoint">000A12</idno><idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Checkpoint">000A12</idno><idno type="wicri:doubleKey">1077-4866:2009:Ocampo A:rationale:modeling:for</idno><idno type="wicri:Area/Main/Merge">003983</idno><idno type="wicri:Area/Main/Curation">003905</idno><idno type="wicri:Area/Main/Exploration">003905</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">Rationale modeling for software process evolution</title><author><name sortKey="Ocampo, Alexis" sort="Ocampo, Alexis" uniqKey="Ocampo A" first="Alexis" last="Ocampo">Alexis Ocampo</name><affiliation wicri:level="3"><country xml:lang="fr">Allemagne</country><wicri:regionArea>Fraunhofer Institute for Experimental Software Engineering Fraunhofer‐Platz 1, 67663 Kaiserslautern</wicri:regionArea><placeName><region type="land" nuts="2">Rhénanie-Palatinat</region><settlement type="city">Kaiserslautern</settlement></placeName></affiliation><affiliation wicri:level="1"><country wicri:rule="url">Allemagne</country></affiliation><affiliation wicri:level="3"><country xml:lang="fr">Allemagne</country><wicri:regionArea>Correspondence address: Fraunhofer Institute for Experimental Software Engineering Fraunhofer‐Platz 1, 67663 Kaiserslautern</wicri:regionArea><placeName><region type="land" nuts="2">Rhénanie-Palatinat</region><settlement type="city">Kaiserslautern</settlement></placeName></affiliation></author><author><name sortKey="Munch, Jurgen" sort="Munch, Jurgen" uniqKey="Munch J" first="Jürgen" last="Münch">Jürgen Münch</name><affiliation wicri:level="3"><country xml:lang="fr">Allemagne</country><wicri:regionArea>Fraunhofer Institute for Experimental Software Engineering Fraunhofer‐Platz 1, 67663 Kaiserslautern</wicri:regionArea><placeName><region type="land" nuts="2">Rhénanie-Palatinat</region><settlement type="city">Kaiserslautern</settlement></placeName></affiliation></author></analytic><monogr></monogr><series><title level="j" type="main">Software Process: Improvement and Practice</title><title level="j" type="alt">SOFTWARE PROCESS: IMPROVEMENT AND PRACTICE</title><idno type="ISSN">1077-4866</idno><idno type="eISSN">1099-1670</idno><imprint><biblScope unit="vol">14</biblScope><biblScope unit="issue">2</biblScope><biblScope unit="page" from="85">85</biblScope><biblScope unit="page" to="105">105</biblScope><biblScope unit="page-count">21</biblScope><publisher>John Wiley & Sons, Ltd.</publisher><pubPlace>Chichester, UK</pubPlace><date type="published" when="2009-03">2009-03</date></imprint><idno type="ISSN">1077-4866</idno></series></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">1077-4866</idno></seriesStmt></fileDesc><profileDesc><textClass><keywords scheme="Teeft" xml:lang="en"><term>Adaptive services grid</term><term>Aerospace engineering standards</term><term>Application engineering</term><term>Armbrust</term><term>Artifact</term><term>Best practices</term><term>Bruegge</term><term>Case studies</term><term>Common issues</term><term>Compliant</term><term>Computer science</term><term>Conceptual</term><term>Conceptual model</term><term>Conradi</term><term>Copyright</term><term>Database</term><term>Design rationale</term><term>Design rationale domain</term><term>Dutoit</term><term>Ecss</term><term>Ecss requirement</term><term>Ecss software engineering standards</term><term>Ecss standards</term><term>European workshop</term><term>Evolution</term><term>External services</term><term>Ground segments</term><term>Heuristic</term><term>Ieee</term><term>Ight software</term><term>International organization</term><term>John wiley sons</term><term>Lecture notes</term><term>Modeling</term><term>Ocampo</term><term>Organizational process</term><term>Pract</term><term>Process changes</term><term>Process description</term><term>Process element</term><term>Process elements</term><term>Process engineer</term><term>Process engineers</term><term>Process evolution</term><term>Process knowledge</term><term>Process model</term><term>Process model changes</term><term>Process model evolution</term><term>Process models</term><term>Rationale</term><term>Rationale information</term><term>Rationale management</term><term>Rationale modeling</term><term>Real project</term><term>Reference process</term><term>Reference process model</term><term>Research section</term><term>Research section rationale modeling</term><term>Same time</term><term>Second study</term><term>Semg</term><term>Softw</term><term>Software</term><term>Software developer</term><term>Software engineering</term><term>Software engineers</term><term>Software process</term><term>Software process evolution</term><term>Software process improvement</term><term>Software process technology</term><term>Software processes</term><term>Standardization</term><term>Study results</term><term>Such changes</term><term>Traceability</term><term>Traceability relationships</term><term>Understanding rationale information</term><term>Visualization</term></keywords></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Evolving a software process without a retrospective on its evolution and, in consequence, without an appropriate understanding, can lead to important problems for a software development organization. Two examples of such problems are inefficient performance as a consequence of the arbitrary introduction of changes or difficulty in demonstrating compliance to a given standard. Capturing information on the rationale underlying process changes provides a means for better understanding process evolution. This article presents two studies aimed at understanding and identifying information needs for describing the rationale for process evolution. Additionally, it presents an approach for incrementally evolving processes supported by this rationale. This approach is derived from the results of the studies and a survey of related work. An application of the approach during the evolution of a reference process for developing service‐oriented applications is presented together with experience and open questions for future research work. Copyright © 2008 John Wiley & Sons, Ltd.</div></front></TEI><affiliations><list><country><li>Allemagne</li></country><region><li>Rhénanie-Palatinat</li></region><settlement><li>Kaiserslautern</li></settlement></list><tree><country name="Allemagne"><region name="Rhénanie-Palatinat"><name sortKey="Ocampo, Alexis" sort="Ocampo, Alexis" uniqKey="Ocampo A" first="Alexis" last="Ocampo">Alexis Ocampo</name></region><name sortKey="Munch, Jurgen" sort="Munch, Jurgen" uniqKey="Munch J" first="Jürgen" last="Münch">Jürgen Münch</name><name sortKey="Ocampo, Alexis" sort="Ocampo, Alexis" uniqKey="Ocampo A" first="Alexis" last="Ocampo">Alexis Ocampo</name><name sortKey="Ocampo, Alexis" sort="Ocampo, Alexis" uniqKey="Ocampo A" first="Alexis" last="Ocampo">Alexis Ocampo</name></country></tree></affiliations></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Main/Exploration
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 003905 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 003905 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Lorraine
|area= InforLorV4
|flux= Main
|étape= Exploration
|type= RBID
|clé= ISTEX:8A2034E007FE8B1CC78A54A20E455D4A2AA1D9A0
|texte= Rationale modeling for software process evolution
}}
| This area was generated with Dilib version V0.6.33. |  |